Can someone help me, I'm sure there's a simple solution to this behaviour.
When I build my winsock application I link in the winsock.lib file. When the application starts, if it cannot find a winsock.dll anywhere in the path then it bombs out with a system modal "Cannot find WINSOCK.DLL" and the application never
starts. This message occurs before my applcaition starts and reaches the point
where I call WSAStartUp to test for a valid WINSOCK.DL
If none is found I handle that error correctly, but of course I can't test this since the app
never starts.
I have tried the following to track down what's occurring
1./ I break just before the first winsock call I ever make (WSAStartUp)
2./ I try and load the DLL directly using loadlibrary to see if that fails
3./ Break at the very start of my program
None of these work if there is NO winsock.dll anywhere in the search path
I suspect some startup code has been linked into my app and it is that which is failing. I have tried several winsock.lib's. They are all 4096 bytes long and vary in date.
Has anyone seen this?
Has anyone fixed this?
Who actually controls the winsock.lib
Is there source code for it?
Hope you can help
Paul
paul@insitu.com
From news@bigblue.oit.unc.edu Fri Mar 4 02:35:26 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA03138; Thu, 3 Mar 1994 21:58:00 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA06896; Thu, 3 Mar 1994 21:35:27 -0500
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)